[rtl] add err_o signal to IMEM modules #273
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If the IMEM is implemented as true ROM any write attempt will raise a _store access fault_ exception with "[DEVICE_ERR]" error code (from the BUSKEEPER)
add err_o signal to IMEM module(s)
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds the
err_osignal to the IMEM module(s). This signal is set if the IMEM is implemented as true ROM and software attempts to perform a write access to it, which will create a "device error".If there is a write access to a read-only IMEM the 📚 default runtime environment trap handler will output an error message (in this example: store 32-bit word to address 0x0000_0004):
edit
This PR also add the
err_osignal to the processor's BOOTROM.ℹ️ Before this PR write access to the IMEM also raised a bus exception by not asserting the IMEM's
ack_osignal, which resulted in a "device timeout error":